Comparing extracted card data with user data

ABSTRACT

Extracting card data comprises receiving, by one or more computing devices, a digital image of a card; perform an image recognition process on the digital representation of the card; identifying an image in the digital representation of the card; comparing the identified image to an image database comprising a plurality of images and determining that the identified image matches a stored image in the image database; determining a card type associated with the stored image and associating the card type with the card based on the determination that the identified image matches the stored image; and performing a particular optical character recognition algorithm on the digital representation of the card, the particular optical character recognition algorithm being based on the determined card type. Another example uses an issuer identification number to improve data extraction. Another example compares extracted data with user data to improve accuracy.

RELATED APPLICATION

This application claims priority under 35 U.S.C. §119 to U.S. PatentApplication No. 61/841,260 filed Jun. 28, 2013 and entitled “ExtractingCard Data Using Card Art.” The entire contents of the above-identifiedapplication are hereby fully incorporated herein by reference.

TECHNICAL FIELD

The technology disclosed herein pertains to extracting financial cardinformation, and more particularly to using card art, the issueridentification number (“IIN”) database, and user data to improve theextraction process.

BACKGROUND

When consumers make online purchases or purchases using mobile devices,they are often forced to enter credit card information into the mobiledevice for payment. Due to the small screen size and keyboard interfaceon a mobile device, such entry is generally cumbersome and prone toerrors. Users may use many different cards for purchases, such as creditcards, debit cards, stored value cards, and other cards. Informationentry difficulties are multiplied for a merchant attempting to processmobile payments on mobile devices for multiple transactions.

Current applications for obtaining payment information from a paymentcard require a precise positioning of the card in the scan. Typically, abox is presented on the user interface of the user computing device. Theuser is required to precisely line the card up within the box to allowthe user computing device to recognize the card.

Current applications do not utilize other available data, such as cardart, the issuer identification number (“IIN”) database, or user data toimprove the extraction process.

SUMMARY

The technology of the present disclosure includes computer-implementedmethods, computer program products, and systems for extracting carddata. Extracting card data comprises receiving, by one or more computingdevices, a digital image of a card; perform an image recognition processon the digital representation of the card; identifying an image in thedigital representation of the card; comparing the identified image to animage database comprising a plurality of images and determining that theidentified image matches a stored image in the image database;determining a card type associated with the stored image and associatingthe card type with the digital representation of the card based at leastin part on the determination that the identified image matches thestored image; and performing a particular optical character recognitionalgorithm on the digital representation of the card, the particularoptical character recognition algorithm being based at least in part onthe determined card type. Another example uses an issuer identificationnumber to improve data extraction. Another example compares extracteddata with user data to improve accuracy.

These and other aspects, objects, features, and advantages of theexample embodiments will become apparent to those having ordinary skillin the art upon consideration of the following detailed description ofillustrated example embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a system for extracting financialaccount information from a card, in accordance with certain exampleembodiments of the technology disclosed herein.

FIG. 2 is a block flow diagram depicting methods for extractingfinancial account information using card art, in accordance with certainexample embodiments.

FIG. 3 is a block flow diagram depicting methods for identifying cardtypes based on images on cards, in accordance with certain exampleembodiments.

FIG. 4 is a block flow diagram depicting methods for extractingfinancial account information using a checksum algorithm, in accordancewith certain example embodiments.

FIG. 5 is a block flow diagram depicting methods for performing achecksum algorithm on extracted information, in accordance with certainexample embodiments.

FIG. 6 is a block flow diagram depicting for extracting financialaccount information using the IIN database, in accordance with certainexample embodiments.

FIG. 7 is a block flow diagram depicting methods for comparing extractedcard information to analyzed user data, in accordance with certainexample embodiments.

FIG. 8 is a block flow diagram depicting methods for extractingfinancial account information using user data, in accordance withcertain example embodiments.

FIG. 9 is an illustration of a user computing device displaying an imageof a financial card, in accordance with certain example embodiments.

FIG. 10 is a block diagram depicting a computing machine and a module,in accordance with certain example embodiments.

DETAILED DESCRIPTION OF THE EXAMPLE EMBODIMENTS Overview

Embodiments herein provide computer-implemented techniques for allowinga user computing device to extract financial card information usingoptical character recognition (“OCR”). The process of extractingfinancial card information may use image recognition of the card art toimprove the OCR. Determining the type of card based on the card art mayallow the OCR application to limit or bias the OCR results to datarelated to the card type. The process of extracting financial cardinformation can be improved by using a checksum algorithm on thefinancial account information. The checksum algorithm can be used toverify that the extracted account number is a valid number. The processof extracting financial card information can be improved by using anissuer identification number (“IIN”) database to bias the OCR search.The IIN database can be used to verify that parts of the extractedaccount number are valid numbers and to determine the card type.Determining the type of card based on the IIN database allows the OCRapplication to limit or bias the OCR results to data related to the cardtype. Additionally, the process of extracting financial card informationcan be improved by using user data to verify or bias useridentification.

Throughout the specification, the general term “card” will be used torepresent any type of physical card instrument, such as a magneticstripe card. In example embodiments, the different types of cardrepresented by “card” can include credit cards, debit cards, storedvalue cards, loyalty cards, identification cards, or any other suitablecard representing an account or other record of a user or otherinformation thereon. Example embodiments described herein may be appliedto the images of other items, such as receipts, boarding passes,tickets, and other suitable items. The card may also be an image orfacsimile of the card. For example, the card may be a representation ofa card on a display screen or a printed image of a card.

The user may employ the card when making a transaction, such as apurchase, ticketed entry, loyalty check-in, or other suitabletransaction. The user may obtain the card information for the purpose ofimporting the account represented by the card into a digital walletapplication module of a computing device or for other digital accountpurposes. The card is typically a plastic card containing the accountinformation and other data on the card. In many card embodiments, thecustomer name, expiration date, and card numbers are physically embossedor otherwise written on the card. The embossed information is visiblefrom both the front and back of the card, although the embossedinformation is typically reversed on the back of the card.

A user may desire to enter the information from the card into a mobileuser computing device or other computing device, for example, to conductan online purchase, to conduct a purchase at a merchant location, to addthe information to a wallet application on a user computing device, orfor any other suitable reason. In an example, the user desires to use amobile computing device to conduct a purchase transaction using adigital wallet application module executing on the mobile computingdevice. The digital wallet application module may require an input ofthe details of a particular user payment account to conduct atransaction with the particular user payment account or to set up theaccount. Due to the small screen size and keyboard interface on a mobiledevice, such entry can be cumbersome and error prone for manual input.Additionally, a merchant system may need to capture card information toconduct a transaction or for other reasons.

In addition to account identifiers, the front of the card typicallycontains logos of the issuer of the card, pictures chosen by the user orthe issuer, other text describing the type or status of the useraccount, a security code, and other marketing and security elements,such as holograms or badges. The name, card expiration date, and theaccount identifier, such as a credit card number, may be embossed on thefront of the card such that the information protrudes from the front ofthe card.

The user employs a mobile phone, digital camera, or other user computingdevice to capture an image of the card associated with the account thatthe user desires to input into the user computing device. The image maybe obtained from the camera module of a user computing device, such asthe camera on a mobile phone. The image may be obtained from a scannercoupled to the user computing device or any other suitable digitalimaging device. The image may be obtained from video captured by theuser computing device. The image may be accessed from a storage locationon the user computing device, from a remote storage location, or fromany suitable location. All sources capable of providing the image willbe referred to herein as a “camera.”

An OCR application receives the image of the card from the camera. Thefunctions of the OCR application may be performed by any suitablemodule, hardware, software, or application operating on the usercomputing device. Some, or all, of the functions of the OCR applicationmay be performed by a remote server or other computing device, such asthe server operating in an OCR system. For example, a digital walletapplication module on the user computing device may obtain the image ofthe card and transmit the image to the OCR system for processing. Inanother example, some of the OCR functions may be conducted by the usercomputing device and some by the OCR system or another remote server.Examples provided herein may indicate that many of the functions areperformed by an OCR application on the user computing device, but someor all of the functions may be performed by any suitable computingdevice.

The image is presented on the user interface of the user computingdevice as a live video image of the financial card. The OCR applicationcan isolate and store one or more images from the video feed of thecamera. For example, the user may hover the camera function of a usercomputing device over a financial card and observe the representation ofthe financial card on the user interface of the user computing device.The user may actuate or real or virtual button on the user computingdevice to capture a preferred image. The OCR application may select thepreferred image automatically.

The OCR application, the camera module, or the user computing device, orother computing device performs blur detection on the image. The imagemay be recognized as blurry, overly bright, overly dark, or otherwiseobscured in a manner that prevents a high resolution image from beingobtained. The OCR application, or other computing device, may adjust theimage capturing method to reduce the blur in the image. For example, theOCR application may direct the camera to adjust the focus on thefinancial card. In another example, the OCR application may direct theuser to move the camera closer to, or farther away from, the financialcard. In another example, the OCR application may perform a digitalimage manipulation to remove the blur. Any other suitable method ofcorrecting a blurred image can be utilized.

The OCR application isolates the image of the card. The OCR applicationcan use any image data manipulation or image extraction to isolate thecard image.

The OCR application may crop out a portion of the image to display onlythe desired information from the card. For example, if the card in theimage is a credit card, the OCR application accesses informationassociated with the expected location of the account number of a creditcard. The expected location may be obtained from a database of cardlayouts stored on the user computing device or in another suitablelocation. For example, credit cards, driver's licenses, loyalty cards,and other cards typically meet an industry standard for the datalocations and the layout of the card. The industry standards may bestored in the OCR application or in a location accessible by the OCRapplication.

The OCR application performs an image recognition algorithm on the cardimage. The OCR application may use any suitable algorithm, process,method, or other manner of recognizing card images. For example, the OCRapplication may isolate images, such as card art, within the image ofthe card and can compare the card art images to a stored database ofimages to identify matching images. The OCR application may apply an OCRalgorithm to one or more words identified in the card art.

The OCR application identifies images, logos, words, icons, pictures,badges, and other features of the art on the card image. The OCRapplication extracts the identity of an image from the informationassociated with a matching image in the database. For example, when theOCR application compares the identified art to a database of images andlocates a matching image, the OCR application accesses any data storedwith the matching image.

The data stored with the matching images may include an identificationof the card type. For example, the OCR application may identify a logoon the card image that matches a logo in the database. The logo may beidentified in the database as the logo for a particular bank. In thisexample, the OCR application may identify the card image as likely beinga debit card associated with the particular credit card issuer.

In another example, the OCR application may identify an image thatmatches an image in the database of a character associated with aparticular department store, such as a cartoon mascot. The OCRapplication may identify the card image as likely being a gift cardissued by the particular department store.

In another example, the OCR application may identify a hologram thatmatches an image in the database that is associated with a particularcredit card issuer. The OCR application may recognize the hologram bycomparing multiple images from multiple angles with images in the imagedatabase. The multiple images may be obtained by extracting images froma continuous scan of the card or by capturing multiple images of thecard by moving the camera to multiple angles above the card. The OCRapplication may identify the card as likely being a credit card issuedby the particular credit card issuer associated with the hologram.

The OCR application applies an OCR algorithm to the card image toidentify the information on the card. The OCR algorithm may representany suitable process, program, method, or other manner of recognizingthe digits or characters represented on the card image. The OCRapplication may improve the accuracy and speed of the OCR algorithm byusing the information obtained in the image recognition process. Forexample, the OCR application may have determined that a hologram on thecard image matches a hologram associated with a particular credit cardcompany. The OCR application can use an OCR algorithm that is customizedfor credit cards from the particular credit card company. The OCRalgorithm may be customized to look for characters in particularlocations on the card image. The OCR algorithm may be customized to lookfor a certain number of characters. The OCR algorithm may be customizedto look for certain combinations of characters. The OCR algorithm may becustomized to know that the cards from the particular credit cardcompany typically have certain data on the reverse side of the card. TheOCR algorithm may be customized to know which characters are typicallyembossed. The OCR algorithm may be customized to look for any configuredarrangements, data locations, limitations, card types, characterconfigurations, or other suitable card data.

The OCR application extracts the relevant card information from the cardimage. The OCR application identifies each character and categorizes thegroups of characters. For example, the OCR application may determinethat a group of characters comprise a name, account number, expirationdate, and other suitable categories of data. The OCR applicationdisplays the extracted data on a user interface to the user to allow theuser to verify or edit the data.

The OCR algorithm may be customized to bias the results to matchexpected card data. In an example, the OCR algorithm has a confidencelevel of 60% that the first digit of the user account number is an 8 anda 40% confidence level that the first digit of the user account numberis a 4. The OCR algorithm may recognize that the first digit of a creditcard from the identified card issuer is typically a 4. The OCR algorithmmay reject the higher confidence result and present the 4 as the bestresult.

In certain situations, the OCR application may display more than one setof data when the OCR application has a lower confidence in the results.That is, if the confidence level in the result is below a configuredthreshold, the OCR application may display the top two results forcertain digits and allow the user to select the correct digit.

The OCR application supplies the extracted data to a digital walletapplication module, point of sale terminal, website, or any suitableapplication or system that the user desires. The extracted data may beused by an application on the user computing device. The extracted datamay be transmitted via an Internet connection over the network, via anear field communication (“NFC”) technology, emailed, texted, ortransmitted in any suitable manner.

In another example, the OCR application can apply a checksum algorithmto the extracted card information. A checksum algorithm is amathematical procedure that is applied to a set of data for the purposeof detecting errors that may have been introduced during the OCRprocess. A checksum algorithm produces a result from a mathematicalmanipulation of the numbers that can be compared to an expected result.If the calculated result does not match the expected result, then theset of data may contain an error. If the calculated result matches theexpected result, then the data is likely not to contain an error.

An example of a checksum algorithm is the Luhn algorithm. The Luhnalgorithm is a checksum formula used to validate a variety ofidentification numbers, such as credit card numbers. The OCR applicationmay apply the Luhn algorithm to a set of digits that are suspected ofbeing the account number of a credit card. That is, the OCR applicationmay extract the data from a card image, categorize a certain set ofcharacters as a credit card number, and perform a Luhn algorithm test onthe digits. If the set of digits results in an expected result, then theOCR application assesses a higher confidence that the digits were readaccurately.

If the OCR application applies a checksum algorithm, such as the Luhnalgorithm, and does not generate the expected result, then the OCRapplication may perform the OCR process on the selected digits again.The OCR application may perform the OCR process on an alternate set ofdigits on the card image. The OCR application may request digit entryassistance from the user. The OCR application can perform any suitableprocedure upon a determination that the checksum was invalid.

The OCR application may use the Luhn algorithm to choose among variousoptions for digits when more than one option is available for a singlecharacter. In an example, the applying of the OCR algorithm on an imageof a credit card produces the following options that appear possibleprobabilistically:

(a) 4000 0008 0080 0002

(b) 4000 0000 0080 0002

(c) 4000 0008 0000 0002

(d) 4000 0000 0000 0002

Running the Luhn checksum on each of these possibilities will result inonly (d) passing the Luhn checksum. Therefore, (d) is the most likelycard number.

In another example embodiment, the OCR application uses an issueridentification number (“IIN”) database to improve the data extractionprocess. The first two to six digits of a credit card or debit cardaccount number are typically used as the issuer identification number.The IIN identifies the institution that issued the credit card to thecard holder.

The OCR application captures an image of a card and determines thelikely location of the account number. The OCR application may utilizethe methods disclosed herein or any suitable method. The likely locationof the account number may be based on an analysis of account numberlocations stored in a database or other suitable location assessablefrom the OCR application. The OCR application may crop the card image toisolate the account number location to allow easier analysis.

The OCR application applies an OCR algorithm or other process toidentify the first six digits of the account number that typicallyaccount for the IIN. The OCR application compares the extracted digitsto an IIN database.

The OCR application may access a database of IINs on the user computingdevice, on a storage location on a server associated with a paymentprocessing system or an OCR system, or in any suitable storage location.The OCR application determines if the extracted digits match any of theIINs in the IIN database.

If extracted digits match any of the IINs in the IIN database, the OCRapplication determines from the information in the database the type ofcard with which the IIN is associated. For example, the OCR applicationmay determine that the card is a credit card, debit card, stored valuecard, or another type of card. The OCR application may determine theissuer of the card. The OCR application may determine a financialinstitution associated with the card. Any other suitable information maybe determined from the information associated with the database.

The OCR application employs an OCR algorithm or other computerimplemented process to determine the card information. For example, theOCR application may use an OCR program to analyze the image of the cardor the cropped image to extract the financial account number of a creditcard. The extracted number may be presented to the user forverification, stored in the OCR application, transmitted to a remotecomputer, stored in a digital wallet application module, or used in anysuitable manner. Other information, such as the name, expiration date,security code, or any suitable information, can also be extracted fromthe image.

The OCR application may improve the accuracy and speed of the OCRalgorithm by using the information determined from the IIN database. Forexample, the OCR application may have determined that the IIN matchesthe IIN associated with a particular credit card company. The OCRapplication can use an OCR algorithm that is customized for credit cardsfrom the particular credit card company. The OCR algorithm may becustomized to look for characters in particular locations on the cardimage. The OCR algorithm may be customized to look for a certain numberof characters. The OCR algorithm may be customized to look for certaincombinations of characters. The OCR algorithm may be customized to knowthat the cards from the particular credit card company typically havecertain data on the reverse side of the card. The OCR algorithm may becustomized to know which characters are typically embossed. The OCRalgorithm may be customized to look for any configured arrangements,data locations, limitations, card types, character configurations, orother suitable card data. The OCR algorithm may be customized to biasthe results to match expected card data. For example, if a particularcard type is identified from the IIN database, the information from thedatabase may provide the user identification number arrangement for thatcard type. The database may indicate that a particular credit cardissuer uses a 16 digit user identification number while another creditcard issuer may use a 15 digit user identification number. The OCRalgorithm may use the digit arrangement to improve the accuracy of theOCR algorithm.

If the OCR application does not identify a match in the UN database thenthe OCR application may perform the OCR process on the selectedcharacters again. The OCR application may perform the OCR process on analternate set of characters on the card image. The OCR application maydetermine that a customized OCR algorithm is not available for theextracted IIN and use a general OCR algorithm. The OCR application mayrequest IIN number assistance from the user. The OCR application canperform any suitable procedure upon a determination that the IIN is notmatched in the IIN database.

In another example, the OCR application analyses user data before orafter applying an OCR algorithm to the card image. The OCR applicationcan obtain data from one or more sources on the user computing device orother suitable locations. For example, the user may provide the OCRapplication access to a list of names on a contact list of the user onthe user computing device, in a cloud computing environment, on a serversystem, or in any suitable location. The user may provide the OCRapplication access to other accounts of the user, such as a socialnetwork account, an email account, or other suitable accounts.

The OCR application may use the sources of names to customize the OCRalgorithm to make the OCR process more accurate. The OCR application mayuse the names from the lists as a bias in the OCR process. That is, ifthe OCR algorithm has generated two possible last names for the user,the OCR algorithm may determine if either of the candidate names isrepresented in the user data and select that name. If a name with aparticular spelling is represented in the user data, the OCR algorithmmay interpret that entry as an indication that the name of the user isalso spelled in the same manner and bias the results of the OCRalgorithm to reflect that spelling.

The OCR algorithm may use the names extracted for other card accounts ofthe user and the names associated with other user accounts as a bias forthe OCR process. The OCR algorithm may access the names associated withother accounts in the digital wallet application module or in anotheraccount application.

The OCR algorithm may use the data to verify the extracted data or toprovide a bias for the OCR algorithm. If the OCR application does notidentify a match in the user data then the OCR application may performthe OCR process on the selected characters again. The OCR applicationmay perform the OCR process on an alternate set of characters on thecard image. The OCR application may request user data assistance fromthe user.

Example System Architecture

Turning now to the drawings, in which like numerals represent like (butnot necessarily identical) elements throughout the figures, exampleembodiments are described in detail.

FIG. 1 is a block diagram depicting a system for extracting financialaccount information with relaxed card alignment and for extractingfinancial account information from multiple cards, in accordance withcertain example embodiments. As depicted in FIG. 1, the system 100includes network computing devices 110, 120, 140, and 170 that areconfigured to communicate with one another via one or more networks 105.In some embodiments, a user associated with a device must install anapplication and/or make a feature selection to obtain the benefits ofthe techniques described herein.

Each network 105 includes a wired or wireless telecommunication means bywhich network devices (including devices 110, 120, 140, and 170) canexchange data. For example, each network 105 can include a local areanetwork (“LAN”), a wide area network (“WAN”), an intranet, an Internet,a mobile telephone network, or any combination thereof. Throughout thediscussion of example embodiments, it should be understood that theterms “data” and “information” are used interchangeably herein to referto text, images, audio, video, or any other form of information that canexist in a computer-based environment.

Each network computing device 110, 120, 140, and 170 includes a devicehaving a communication module capable of transmitting and receiving dataover the network 105. For example, each network device 110, 120, 140,and 170 can include a server, desktop computer, laptop computer, tabletcomputer, a television with one or more processors embedded thereinand/or coupled thereto, smart phone, handheld computer, personal digitalassistant (“PDA”), or any other wired or wireless, processor-drivendevice. In the example embodiment depicted in FIG. 1, the networkdevices 110, 120, 140, and 170 are operated by end-users or consumers,OCR system operators, and payment processing system operators, and cardissuer operators, respectively.

The user 101 can use the communication application 112, which may be,for example, a web browser application or a stand-alone application, toview, download, upload, or otherwise access documents or web pages via adistributed network 105. The network 105 includes a wired or wirelesstelecommunication system or device by which network devices (includingdevices 110, 120, 140, and 170) can exchange data. For example, thenetwork 105 can include a local area network (“LAN”), a wide areanetwork (“WAN”), an intranet, an Internet, storage area network (SAN),personal area network (PAN), a metropolitan area network (MAN), awireless local area network (WLAN), a virtual private network (VPN), acellular or other mobile communication network, Bluetooth, NFC, or anycombination thereof or any other appropriate architecture or system thatfacilitates the communication of signals, data, and/or messages.

The user device 110 may employ a communication module 112 to communicatewith the web server 124 of the OCR system 120 or other servers. Thecommunication module 112 may allow devices to communicate viatechnologies other than the network 105. Examples might include acellular network, radio network, or other communication network.

The user computing device 110 may include a digital wallet applicationmodule 111. The digital wallet application module 111 may encompass anyapplication, hardware, software, or process the user device 110 mayemploy to assist the user 101 in completing a purchase. The digitalwallet application module 111 can interact with the communicationapplication 112 or can be embodied as a companion application of thecommunication application 112. As a companion application, the digitalwallet application module 111 executes within the communicationapplication 112. That is, the digital wallet application module 111 maybe an application program embedded in the communication application 112.

The user device 110 may include an optical character recognition (“OCR”)application 115. The OCR application 115 may interact with thecommunication application 112 or be embodied as a companion applicationof the communication application 112 and execute within thecommunication application 112. In an exemplary embodiment, the OCRapplication 115 may additionally or alternatively be embodied as acompanion application of the digital wallet application module 111 andexecute within the digital wallet application module 111. The OCRapplication 115 may employ a software interface that may open in thedigital wallet application 111 or may open in the communicationapplication 112. The interface can allow the user 101 to configure theOCR application 115.

The OCR application 115 may be used to analyze a card and extractinformation or other data from the card. The OCR system 120 or othersystem that develops the OCR algorithms or other methods may include aset of computer-readable program instructions, for example, usingJavaScript, that enable the OCR system 120 to interact with the OCRapplication 115.

Any of the functions described in the specification as being performedby the OCR application 115 can be performed by the payment processingsystem 140, the OCR system 120, the user computing device 110, thedigital wallet application module 111, a merchant system (not pictured)or any other suitable hardware or software system or application. In anexample, the OCR application 115 on the user computing device 110 mayobtain an image of a card 102 and transmit the image to the OCR system120 to extract the information on the card 102.

The user device 110 includes a data storage unit 113 accessible by theOCR application 115, the web browser application 112, or any suitablecomputing device or application. The exemplary data storage unit 113 caninclude one or more tangible computer-readable media. The data storageunit 113 can be stored on the user device 110 or can be logicallycoupled to the user device 110. For example, the data storage unit 113can include on-board flash memory and/or one or more removable memorycards or removable flash memory.

The user device 110 may include a camera 114. The camera may be anymodule or function of the user computing device 110 that obtains adigital image. The camera 114 may be onboard the user computing device110 or in any manner logically connected to the user computing device110. The camera 114 may be capable of obtaining individual images or avideo scan. Any other suitable image capturing device may be representedby the camera 114.

The user device 110 may include user applications 116. The userapplications 116 may be contact applications, email applications,digital wallet applications, or any applications that may employ thename of the user and/or names of acquaintances of the user. The user mayprovide permission to the OCR application 115 to access the names andother data from the user applications 116. The OCR application 115 mayuse the data from the user applications 116 to verify or improve the OCRprocess.

The payment processing system 140 includes a data storage unit 147accessible by the web server 144. The example data storage unit 147 caninclude one or more tangible computer-readable storage devices. Thepayment processing system 140 is operable to conduct payments between auser 101 and a merchant system (not pictured). The payment processingsystem 140 is further operable to manage a payment account of a user101, maintain a database to store transactions of the merchant systemand the user 101, verify transactions, and other suitable functions.

The user 101 may use a web server 144 on the payment processing system140 to view, register, download, upload, or otherwise access the paymentprocessing system 140 via a website (not illustrated) and acommunication network 105). The user 101 associates one or moreregistered financial card accounts, including bank account debit cards,credit cards, gift cards, loyalty cards, coupons, offers, prepaidoffers, store rewards cards, or other type of financial account that canbe used to make a purchase or redeem value-added services with a paymentaccount of the user 101.

A card issuer, such as a bank or other institution, may be the issuer ofthe financial account being registered. For example, the card issuer maybe a credit card issuer, a debit card issuer, a stored value issuer, afinancial institution providing an account, or any other provider of afinancial account. The payment processing system 140 also may functionas the issuer for the associated financial account. The user's 101registration information is saved in the payment processing system's 140data storage unit 147 and is accessible the by web server 144. The cardissuer employs a card issuer system 170 to issue the cards, manage theuser account, and perform any other suitable functions. The card issuersystem 170 may alternatively be an issue cards used for identification,access, verification, ticketing, or cards for any suitable purpose.

The OCR system 120 utilizes an OCR system web server 124 operating asystem that produces, manages, stores, or maintains OCR algorithms,methods, processes, or services. The OCR system web server 124 mayrepresent the computer-implemented system that the OCR system 120employs to provide OCR services to user computing devices 110, merchantcomputing systems, or any suitable entity. The OCR system web server 124can communicate with one or more payment processing systems 140, a userdevice 110, or other computing devices via any available technologies.Such technologies may include, for example, an Internet connection viathe network 105, email, text, instant messaging, or other suitablecommunication technologies. The OCR system 120 may include a datastorage unit 127 accessible by the web server 124 of the OCR system 120.The data storage unit 127 can include one or more tangiblecomputer-readable storage devices.

Any of the functions described in the specification as being performedby the OCR system 120 can be performed by the OCR application 115, theuser computing device 110, or any other suitable hardware or softwaresystem or application.

Throughout the specification, the general term “card” will be used torepresent any type of physical card instrument, such as the paymentaccount card 102. In example embodiments, the different types of card102 represented by “card” 102 can include credit cards, debit cards,stored value cards, loyalty cards, identification cards, or any othersuitable card representing an account of a user 101 or other informationthereon.

The user 101 may employ the card 102 when making a transaction, such asa purchase, ticketed entry, loyalty check-in, or other suitabletransaction. The user 101 may obtain the card information for thepurpose of importing the account represented by the card 102 into adigital wallet application module 111 of a computing device 110 or forother digital account purposes. The card 102 is typically a plastic cardcontaining the account information and other data on the card 102. Inmany card 102 embodiments, the customer name, expiration date, and cardnumbers are physically embossed on the card 102. The embossedinformation is visible from both the front and back of the card 102,although the embossed information is typically reversed on the back ofthe card 102.

It will be appreciated that the network connections shown are exemplaryand other means of establishing a communications link between thecomputers and devices can be used. Moreover, those having ordinary skillin the art having the benefit of the present disclosure will appreciatethat the user device 110, OCR system 120, payment processing system 140,and card issuer system 170 illustrated in FIG. 1 can have any of severalother suitable computer system configurations. For example, a userdevice 110 embodied as a mobile phone or handheld computer may notinclude all the components described above.

Example Processes

The example methods illustrated in FIGS. 2-8 are described hereinafterwith respect to the components of the example operating environment 100.The example methods of FIGS. 2-8 may also be performed with othersystems and in other environments.

FIG. 2 is a block flow diagram depicting a method 200 for extractingfinancial account information using card art, in accordance with certainexemplary embodiments.

With reference to FIGS. 1 and 2, in block 205, optical characterrecognition (“OCR”) application 115 on the user device 110 obtains adigital scan or image of a card 102. The user 101 employs a mobilephone, digital camera, or other user computing device 110 to capture animage of the card 102 associated with the account that the user 101desires to input into the user computing device 110.

An OCR application 115 on a user computing device 110 receives the imageof the card 102. The image may be obtained from the camera module of auser computing device 110, such as the camera 114 on a mobile phone. Theimage may be obtained from a scanner coupled to the user computingdevice 110 or any other suitable digital imaging device. The image maybe obtained from video captured by the user computing device 110. Theimage may be accessed by the OCR application 115 on the user computingdevice 110 from a storage location on the user computing device 110,from a remote storage location, or from any suitable location. Allsources capable of providing the image will be referred to herein as a“camera” 114.

An OCR application 115 receives the image of the card from the camera.The functions of the OCR application 115 may be performed by anysuitable module, hardware, software, or application operating on theuser computing device. Some, or all, of the functions of the OCRapplication 115 may be performed by a remote server or other computingdevice, such as the server operating in an OCR system 120. For example,a digital wallet application module 111 on the user computing device 110may obtain the image of the card and transmit the image to the OCRsystem 120 for processing. In another example, some of the OCR functionsmay be conducted by the user computing device 110 and some by the OCRsystem 120 or another remote server. Examples provided herein mayindicate that many of the functions are performed by an OCR application115 on the user computing device 110, but some or all of the functionsmay be performed by any suitable computing device.

The image is presented on the user interface of the user computingdevice 110 as a live video image of the card 102 or a single image ofthe card 102. The OCR application 115 can isolate and store one or moreimages from the video feed of the camera 114. For example, the user 101may hover the camera 114 function of a user computing device 110 over acard and observe the representation of the card on the user interface ofthe user computing device 110. An illustration of the card 102 displayedon the user computing device is presented in FIG. 9.

FIG. 9 is an illustration of a user computing device 110 displaying animage of a financial card, in accordance with certain exampleembodiments. The user computing device 110 is shown as a mobilesmartphone. The user computing device 110 is shown with a display screen905 as a user interface. The card 102 is shown displayed on the usercomputing device 110.

Returning to FIG. 2, in block 210, the OCR application 115 isolates theimage of the card. Any image data manipulation or image extraction maybe used to isolate the card image.

The OCR application 115, the camera 114 module, or the user computingdevice 110, or other computing device performs blur detection on theimage. The image may be recognized as blurry, overly bright, overlydark, or otherwise obscured in a manner that prevents a high resolutionimage from being obtained. The OCR application 115, or other computingdevice, may adjust the image capturing method to reduce the blur in theimage. For example, the OCR application 115 may direct the camera 114 toadjust the focus on the financial card. In another example, the OCRapplication 115 may direct the user to move the camera 114 closer to, orfarther away from, the financial card. In another example, the OCRapplication 115 may perform a digital image manipulation to remove theblur. Any other suitable method of correcting a blurred image can beutilized.

In block 215, the OCR application 115 may crop the image to display onlythe desired information from the card 102. For example, if the card 102in the image is a credit card, the OCR application 115 accessesinformation associated with the expected location of the account numberof a credit card. The expected location may be obtained from a databaseof card layouts stored on the user computing device 110 or in anothersuitable location. Credit cards, driver's licenses, loyalty cards, andother cards typically meet an industry standard for the data locationsand the layout of the card. The industry standards may be stored in theOCR application 115 or in a location accessible by the OCR application115. In certain circumstances, the data locations may be provided by theissuer of the card 102.

In block 220, the OCR system 120 or another computing device identifiesthe card type based on images on the card 102.

The details of the method of block 220 are described in greater detailhereinafter with reference to FIG. 3.

FIG. 3 is a block flow diagram depicting methods for identifying cardtypes based on images on cards, in accordance with certain exampleembodiments, as referenced in block 220 of FIG. 2.

In block 305, the OCR application 115 performs an image recognitionalgorithm on the card image. In the example embodiment, the imagerecognition is performed by the OCR application 115 on the usercomputing device 110. In another example, the OCR application 115transmits the image to the OCR system 120 or another suitable computingdevice for the image recognition.

The OCR application 115 may use any suitable algorithm, process, method,or other manner of recognizing card images. For example, the OCRapplication 115 may isolate images, such as card art, within the imageof the card. The OCR application 115 may apply an OCR algorithm to oneor more words identified in the card art. That is, if the imagerecognition algorithm recognizes that a word is represented in the cardart, then an OCR algorithm may be used to identify the word. Forexample, a logo of the card issuer 170 may contain a name or other word.The employed OCR algorithm may be a function of the image recognitionalgorithm, a separate OCR algorithm, or the OCR algorithm used tointerpret the user financial information.

In block 310, the OCR application 115 compares the card art images to astored database of images to identify matching images. The OCRapplication 115 identifies images, logos, words, icons, pictures,badges, and other features of the art on the card image. The card art iscompared to a database storing images associated with card issuers 170.The stored card art may be supplied by card issuers 170 or obtained fromany suitable source. For example, the stored card art may be obtainedfrom websites associated with the card issuers or another suitablewebsite. The stored card art may be supplied by a third party card artprovider. Any suitable source for card art may be used. The stored cardart may be maintained in a database stored on data storage unit 113, OCRsystem data storage unit 127, or another suitable computing device ordata storage unit.

In block 315, the OCR application 115 identifies matches between thecard art and the stored images in the database. For example, aparticular logo in the card art may be a match to a logo in the storedimages to a level of confidence over a configured threshold.

In block 320, the OCR application 115 extracts the identity the card artimage from the information associated with a matching image in thedatabase. For example, when the OCR application 115 compares theidentified art to the database of images and locates a matching image,the OCR application accesses any data stored with the matching image.The stored data may be information about the card issuer 170,information about the issued card, a category of the card, or anysuitable information.

The data stored with the matching images may include an identificationof the card type. For example, the OCR application 115 may identify alogo on the card image that matches a logo in the database. The logo maybe identified in the database as the logo for a particular bank. In thisexample, the card image may be identified as likely being a debit cardassociated with the particular credit card issuer.

In another example, the OCR application 115 may identify an image thatmatches an image in the database of a character associated with aparticular department store, such as a cartoon mascot. In this example,the card image may be identified as likely being a gift card issued bythe particular department store.

In another example, the OCR application 115 may identify a hologram thatmatches an image in the database that is associated with a particularcredit card issuer. The OCR application 115 may recognize the hologramby comparing multiple images from multiple angles with images in theimage database. The multiple images may be obtained by extracting imagesfrom a continuous scan of the card or by capturing multiple images ofthe card by moving the camera to multiple angles above the card. Thecard image may be identified as likely being a credit card issued by theparticular credit card issuer associated with the hologram.

From block 320, the method 220 returns to block 225 in FIG. 2.

In block 225, the OCR application 115 applies an OCR algorithm to thecard image to identify the information on the card 102. The OCRalgorithm may represent any suitable process, program, method, or othermanner of recognizing the digits or characters represented on the cardimage. The accuracy and speed of the OCR algorithm may be improved byusing the information obtained in the image recognition process. Forexample, the OCR application may have determined that a hologram on thecard image matches a hologram associated with a particular credit cardcompany. An OCR algorithm may be used that is customized for creditcards from the particular credit card company. The OCR algorithm may becustomized to look for characters in particular locations on the cardimage. The OCR algorithm may be customized to look for a certain numberof characters. The OCR algorithm may be customized to look for certaincombinations of characters. The OCR algorithm may be customized to knowthat the cards from the particular credit card company typically havecertain data on the reverse side of the card 102. The OCR algorithm maybe customized to know which characters are typically embossed. The OCRalgorithm may be customized to look for any configured arrangements,data locations, limitations, card types, character configurations, orother suitable card data.

In block 230, the OCR application 115 extracts the information, such asthe user identification number from the image of the card 102. Otherinformation, such as the name, expiration date, security code, or anysuitable information, may also be extracted from the image.

The OCR application 115 extracts the relevant card information from thecard image. The OCR application 115 identifies each character andcategorizes the groups of characters. For example, the OCR application115 may determine that a group of characters comprise a name, accountnumber, expiration date, and other suitable categories of data. The OCRapplication 115 displays the extracted data on a user interface to theuser 101 to allow the user 101 to verify or edit the data.

The OCR algorithm may be customized to bias the results to matchexpected card data. In an example, the OCR algorithm has a confidencelevel of 60% that the first digit of the user account number is an 8 anda 40% confidence level that the first digit of the user account numberis a 4. The OCR algorithm may recognize that the first digit of a creditcard from the identified card issuer is typically a 4. The OCR algorithmmay reject the higher confidence result and present the 4 as the bestresult.

In certain situations, the OCR application 115 may display more than oneset of data when the OCR application 115 has a lower confidence in theresults. That is, if the confidence level in the result is below aconfigured threshold, the OCR application 115 may display the top tworesults for certain digits and allow the user 101 to select the correctdigit. The user 101 may signal a selection by actuating a real orvirtual button, tapping the selected digits, or performing any suitableaction.

In an example embodiment, the OCR application 115 displays the extracteddata on the user interface screen of the user computing device 110 toallow easier verification for the user 101. The extracted data may besuperimposed on the image of the card 102. The extracted data may beplaced directly on the associated data in the image or in a positionnear the data in the image. The extracted data may be displayed in acontrasting color to allow for better visibility. For example, if thecard image is a dark color, then the extracted data may be displayed ina white font. All of the extracted data may be displayed on the userinterface at the same time. Alternatively, a portion of the extracteddata may be displayed. After verification by the user 101, the nextportion of the extracted data may be displayed.

For example, the extracted account identification number may bedisplayed just above the location of the account identification numberin the image. Such a placement would allow the user 101 to verify thatthe number was extracted correctly quickly and easily. The user 101would be allowed to verify each number in such a side by sidecomparison. The user 101 may verify the extracted data by selecting areal or virtual button to confirm the data as matching the cardinformation. Any suitable action may be taken by the user 101 to signalverification.

The OCR application 115 may allow the user 101 to highlight, mark, orotherwise identify digits that are not correct. For example, if the nameis extracted with an incorrect letter, the user 101 may tap theincorrect letter. The OCR application 115 may take any suitablecorrective action after the incorrect letter is identified, such asperforming the OCR algorithm again, requesting a corrected digit fromthe user 101, or any suitable action.

In block 235, the OCR application 115 supplies the extracted data to adigital wallet application module 111, point of sale terminal, paymentprocessing system 140, website, or any suitable application or systemthat the user desires. The extracted data may be used by an applicationon the user computing device 110. The extracted data may be transmittedvia an Internet connection over the network 105, via a near fieldcommunication (“NFC”) technology, emailed, texted, or transmitted in anysuitable manner.

FIG. 4 is a block flow diagram depicting a method 400 for extractingfinancial account information using a checksum algorithm, in accordancewith certain example embodiments.

Blocks 205, 210, and 215 are substantially similar to blocks 205, 210,and 215 of FIG. 2 as described herein.

In block 420, the OCR application 115 performs the OCR algorithm to thecard image. The OCR algorithm may represent any suitable process,program, method, or other manner of recognizing the digits or charactersrepresented on the card image.

In block 425, the OCR application 115 extracts the information, such asthe user identification number from the image of the card 102. Otherinformation, such as the name, expiration date, security code, or anysuitable information, may also be extracted from the image.

In block 430, the OCR application 115 performs a checksum algorithm onthe card information. The details of block 430 are described in greaterdetail herein after with reference to FIG. 5.

FIG. 5 is a block flow diagram depicting methods for performing achecksum algorithm on extracted information, in accordance with certainexample embodiments, as referenced in block 430 of FIG. 4.

In block 505, the OCR application 115 determines a checksum algorithmrelevant to the card type. A checksum algorithm is a mathematicalprocedure that is applied to a set of data for the purpose of detectingerrors that may have been introduced during the OCR process. A checksumalgorithm produces a result from a mathematical manipulation of thenumbers that can be compared to an expected result. If the calculatedresult does not match the expected result, then the set of data maycontain an error. If the calculated result matches the expected result,then the data is likely not to contain an error.

The OCR application 115 may determine the type of card being analyzed.For example, the user 101 may input a selection of credit card or debitcard when the OCR application 115 is first initiated. The card type maybe determined based on the appearance of the card image. The OCRapplication 115 may only be configured to be used for particular cardtypes. In an example, the OCR application 115 may extract the data froma card image and categorize a certain set of characters as likely beinga credit card number. Any manner of determining the card type may beemployed. The OCR application 115 accesses a checksum algorithm for theparticular card type from a database of checksum algorithms.

In block 510, the OCR application 115 performs mathematicalmanipulations related to checksum algorithm. An example of a checksumalgorithm is the Luhn algorithm. The Luhn algorithm is a checksumformula used to validate a variety of identification numbers, such ascredit card numbers. The OCR application 115 may perform the Luhnalgorithm on a set of digits that are suspected of being the accountnumber of a credit card. That is, the OCR application 115 may extractthe data from a card image, categorize a certain set of characters as acredit card number, and perform a Luhn algorithm test on the digits.

In block 515, the OCR application 115 compares results of manipulationto expected checksum results. That is, with an accurate card number, thechecksum mathematical manipulation will produce results that meet theexpected results.

In an example, the OCR application 115 may use the Luhn algorithm tochoose among various options for digits when more than one option isavailable for a single character. In an example, the performing of theOCR algorithm on an image of a credit card 102 produces the followingoptions that appear possible probabilistically:

(a) 4000 0008 0080 0002

(b) 4000 0000 0080 0002

(c) 4000 0008 0000 0002

(d) 4000 0000 0000 0002

Running the Luhn checksum on each of these possibilities will result inonly (d) passing the Luhn checksum. Therefore, (d) is the most likelycard number.

In block 520, the OCR application 115 determines validity of theextracted data based on the comparison. That is, the OCR application 115determines if the result of the checksum meets the expected result.

From block 520, the method 430 returns to block 435 of FIG. 4.

Returning to FIG. 4, in block 435, the method 400 determines if theresult of the checksum algorithm was valid. If a result was a validnumber, then the method 400 follows the “YES” branch of block 435 toblock 440. If the result was an invalid number, then the method 400follows the “NO” branch of block 435 to block 420.

Following the NO branch to block 420, the method 400 may reapply the OCRalgorithm and perform the checksum algorithm again as described hereinin blocks 420, 425, and 430. The OCR application 115 may perform the OCRprocess on an alternate set of digits on the card image. The OCRapplication 115 may request digit entry assistance from the user 101.The OCR application 115 may perform any suitable procedure upon adetermination that the checksum was invalid.

Following the YES branch to block 440, the OCR application 115 suppliesthe extracted data to a digital wallet application module 111, point ofsale terminal, payment processing system 140, website, or any suitableapplication or system that the user desires. The extracted data may beused by an application on the user computing device 110. The extracteddata may be transmitted via an Internet connection over the network 105,via a near field communication (“NFC”) technology, emailed, texted, ortransmitted in any suitable manner.

FIG. 6 is a block flow diagram depicting a method 600 for extractingfinancial account information using the UN database, in accordance withcertain example embodiments.

Blocks 205, 210, and 215 of FIG. 6 are substantially similar to blocks205, 210, and 215 of FIG. 2 as described herein.

In block 616, the OCR application 115 performs the OCR algorithm on thearea of the image comprising an issuer identification number (“IIN”) toidentify the IIN on the card 102. The first two to six digits of acredit card or debit card account number are typically used as theissuer identification number. The IIN identifies the card issuer 170that issued the card 102 to the card holder.

The OCR application 115 captures an image of a card and determines thelikely location of the account number. The OCR application 115 mayutilize the methods disclosed herein or any suitable method. The likelylocation of the account number may be based on an analysis of accountnumber locations stored in a database or other suitable locationassessable from the OCR application 115. The OCR application 115 maycrop the card image to isolate the account number location to alloweasier analysis.

The OCR application 115 performs an OCR algorithm other process toidentify the first six digits of the account number that typicallyaccount for the IIN. The OCR application 115 may use information knownabout the user 101 to improve the accuracy of the process. For example,the OCR application 115 may have stored information such as the locationof residence of the user 101. In the example, the OCR application 115may limit the search of the IIN database to a group of IINs that areassociated with the location of the user 101. That is, if the user 101resides in the United States, the OCR application 115 may only search adatabase of IINs that are associated with cards valid in the UnitedStates. If the OCR application 115 has stored information that the useronly uses debit cards, then the OCR application 115 may only search adatabase of IINs that are associated with debit cards. Any other dataassociated with the user 101 may be used to improve the IIN databasesearch and the matching process.

In another example, the OCR application 115 may perform an imagerecognition algorithm on the image. The image recognition algorithm maybe performed in a similar manner as the method 200 described herein. Theimage recognition algorithm may determine that the card 102 in the imagewas issued by a particular card issuer 170. For example, the card 102may be identified as being a credit card from a particular credit cardissuer 170. The OCR application 115 may limit the available IINs thatare possible for the image based on the identified card type. A smallerlist of possible IINs may allow the OCR application 115 to moreaccurately determine the IIN of the card 102 in the image.

In block 620, the OCR application 115 compares the extracted digits toan IIN database. The OCR application 115 may access a database of IINson the user computing device 110, on a storage location on a serverassociated with a payment processing system 140 or an OCR system 120, orin any suitable storage location. The OCR application 115 determines ifthe extracted digits match any of the IINs in the IIN database. If amatch exists, then the IIN number is determined to be valid.

If a result was a valid number, then the method 600 follows the “YES”branch of block 625 to block 627. If the result was an invalid number,then the method 600 follows the “NO” branch of block 625 to block 616.

Following the NO branch to block 616, the method 600 may perform the OCRalgorithm again as described herein in blocks 616 and 620. The OCRapplication 115 may perform the OCR process on an alternate set ofdigits on the card image. The OCR application 115 may request digitentry assistance from the user 102. The OCR application 115 maydetermine that a customized OCR algorithm is not available for theextracted IIN and use a general OCR algorithm. The OCR application 115may request IIN number assistance from the user. The OCR application 115may perform any suitable procedure upon a determination that the IIN isnot matched in the IIN database.

If the OCR application does not identify a match in the IIN databasethen the OCR application may perform the OCR process on the selectedcharacters again. The OCR application may perform the OCR process on analternate set of characters on the card image.

Following the YES branch to block 627, the OCR application 115 performsthe OCR algorithm on the full image based on the card type identifiedfrom the IIN database. If extracted digits match any of the IINs in theIIN database, the OCR application 115 determines from the information inthe database the type of card 102 with which the IIN is associated. Forexample, the OCR application 115 may determine that the card 102 is acredit card, debit card, stored value card, or another type of card. TheOCR application 115 may determine the issuer of the card 102. The OCRapplication 115 may identify a financial institution associated with thecard 102. Any other suitable information may be determined from theinformation associated with the database.

The OCR application 115 employs an OCR algorithm or other computerimplemented process to determine the card information. For example, theOCR application 115 may use an OCR program to analyze the image of thecard 102 or the cropped image to extract the financial account number ofa credit card. Other information, such as the name, expiration date,security code, or any suitable information, may be extracted from theimage.

The OCR application 115 may improve the accuracy and speed of the OCRalgorithm by using the information determined from the IIN database. Forexample, the OCR application 115 may have determined that the IINmatches the IIN associated with a particular credit card company. TheOCR application 115 may use an OCR algorithm that is customized forcredit cards from the particular credit card company. The OCR algorithmmay be customized to look for characters in particular locations on thecard image. The OCR algorithm may be customized to look for a certainnumber of characters. The OCR algorithm may be customized to look forcertain combinations of characters. The OCR algorithm may be customizedto know that the cards from the particular credit card company typicallyhave certain data on the reverse side of the card. The OCR algorithm maybe customized to know which characters are typically embossed. The OCRalgorithm may be customized to look for any configured arrangements,data locations, limitations, card types, character configurations, orother suitable card data. The OCR algorithm may be customized to biasthe results to match expected card data. For example, if a particularcard type is identified from the IIN database, the information from thedatabase may provide the user identification number arrangement for thatcard type. The database may indicate that a particular credit cardissuer uses a 16 digit user identification number while another creditcard issuer may use a 15 digit user identification number. The OCRalgorithm may use the digit arrangement to improve the accuracy of theOCR algorithm.

Blocks 230 and 235 of FIG. 6 are substantially similar to blocks 230 and235 of FIG. 2.

FIG. 7 is a block flow diagram depicting a method 7 for comparingextracted card information to analyzed user data, in accordance withcertain example embodiments.

Blocks 205 and 210 of FIG. 7 are substantially similar to blocks 205 and210 of FIG. 2 as described herein.

In block 715, the OCR application 115 analyses user applications 116,such as user contact lists and other data, before or after applying anOCR algorithm to the card image. The OCR application 115 can obtain datafrom one or more sources on the user computing device 110 or othersuitable locations. For example, the user 101 may provide the OCRapplication 115 access to a list of names on a contact list of the user101 on the user computing device 110, in a cloud computing environment,on a server system, or in any suitable location. The user 101 mayprovide the OCR application 115 access to other accounts of the user101, such as a social network account, an email account, or othersuitable accounts.

In block 235, the OCR application extracts relevant card information asdescribed in block 235 of FIG. 2.

In block 736, the OCR application 115 compares extracted cardinformation to analyzed user data. Block 736 is described in greaterdetail hereinafter with reference to FIG. 8.

FIG. 8 is a block flow diagram depicting a method 736 for extractingfinancial account information using user data, in accordance withcertain example embodiments, as referenced in block 736 of FIG. 7.

In block 805, the OCR application 115 accesses stored informationassociated with user 101. The names may be extracted from contact lists,email applications, user social networks, and other suitable userapplications 116, information from which may be stored on the userdevice 110, the OCR system 120, or another suitable location.

In block 810, the OCR application 115 compares extracted informationfrom the card image with the stored information. Names and other datafrom the stored information are compared to the extracted name from thecard to look for matches. For example, the name of the user may berepresented in the stored information.

In block 815, the OCR application 115 determines if information from thecard image matches the stored information. In an example, twenty namesin the contact list of the user are spelled “Smith”; however, the OCRalgorithm determined that the name is “Snith.” The OCR application 115would determine that the information from the card image does not matchthe stored information.

From block 815, the method 736 returns to block 738 of FIG. 7.

Returning to FIG. 7, if the information from the card image matches thestored information, then the method 700 follows the “YES” branch ofblock 738 to block 235. If the information from the card image does notmatch the stored information, then the method 700 follows the “NO”branch of block 738 to block 230.

Following the NO branch to block 230, the method 700 may perform themethod again as described herein in blocks 230 and 736. The OCRapplication 115 may perform the OCR process on an alternate set ofdigits on the card image. The OCR application 115 may request digitentry assistance from the user 102. The OCR application 115 may requestname assistance from the user. The OCR application 115 may perform anysuitable procedure upon a determination that user data does not matchthe stored information.

Block 235 is substantially similar to block 235 of FIG. 2.

Other Example Embodiments

FIG. 10 depicts a computing machine 2000 and a module 2050 in accordancewith certain example embodiments. The computing machine 2000 maycorrespond to any of the various computers, servers, mobile devices,embedded systems, or computing systems presented herein. The module 2050may comprise one or more hardware or software elements configured tofacilitate the computing machine 2000 in performing the various methodsand processing functions presented herein. The computing machine 2000may include various internal or attached components such as a processor2010, system bus 2020, system memory 2030, storage media 2040,input/output interface 2060, and a network interface 2070 forcommunicating with a network 2080.

The computing machine 2000 may be implemented as a conventional computersystem, an embedded controller, a laptop, a server, a mobile device, asmartphone, a set-top box, a kiosk, a vehicular information system, onemore processors associated with a television, a customized machine, anyother hardware platform, or any combination or multiplicity thereof. Thecomputing machine 2000 may be a distributed system configured tofunction using multiple computing machines interconnected via a datanetwork or bus system.

The processor 2010 may be configured to execute code or instructions toperform the operations and functionality described herein, managerequest flow and address mappings, and to perform calculations andgenerate commands. The processor 2010 may be configured to monitor andcontrol the operation of the components in the computing machine 2000.The processor 2010 may be a general purpose processor, a processor core,a multiprocessor, a reconfigurable processor, a microcontroller, adigital signal processor (“DSP”), an application specific integratedcircuit (“ASIC”), a graphics processing unit (“GPU”), a fieldprogrammable gate array (“FPGA”), a programmable logic device (“PLD”), acontroller, a state machine, gated logic, discrete hardware components,any other processing unit, or any combination or multiplicity thereof.The processor 2010 may be a single processing unit, multiple processingunits, a single processing core, multiple processing cores, specialpurpose processing cores, co-processors, or any combination thereof.According to certain example embodiments, the processor 2010 along withother components of the computing machine 2000 may be a virtualizedcomputing machine executing within one or more other computing machines.

The system memory 2030 may include non-volatile memories such asread-only memory (“ROM”), programmable read-only memory (“PROM”),erasable programmable read-only memory (“EPROM”), flash memory, or anyother device capable of storing program instructions or data with orwithout applied power. The system memory 2030 may also include volatilememories such as random access memory (“RAM”), static random accessmemory (“SRAM”), dynamic random access memory (“DRAM”), and synchronousdynamic random access memory (“SDRAM”). Other types of RAM also may beused to implement the system memory 2030. The system memory 2030 may beimplemented using a single memory module or multiple memory modules.While the system memory 2030 is depicted as being part of the computingmachine 2000, one skilled in the art will recognize that the systemmemory 2030 may be separate from the computing machine 2000 withoutdeparting from the scope of the subject technology. It should also beappreciated that the system memory 2030 may include, or operate inconjunction with, a non-volatile storage device such as the storagemedia 2040.

The storage media 2040 may include a hard disk, a floppy disk, a compactdisc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), aBlu-ray disc, a magnetic tape, a flash memory, other non-volatile memorydevice, a solid state drive (“SSD”), any magnetic storage device, anyoptical storage device, any electrical storage device, any semiconductorstorage device, any physical-based storage device, any other datastorage device, or any combination or multiplicity thereof. The storagemedia 2040 may store one or more operating systems, application programsand program modules such as module 2050, data, or any other information.The storage media 2040 may be part of, or connected to, the computingmachine 2000. The storage media 2040 may also be part of one or moreother computing machines that are in communication with the computingmachine 2000 such as servers, database servers, cloud storage, networkattached storage, and so forth.

The module 2050 may comprise one or more hardware or software elementsconfigured to facilitate the computing machine 2000 with performing thevarious methods and processing functions presented herein. The module2050 may include one or more sequences of instructions stored assoftware or firmware in association with the system memory 2030, thestorage media 2040, or both. The storage media 2040 may thereforerepresent examples of machine or computer readable media on whichinstructions or code may be stored for execution by the processor 2010.Machine or computer readable media may generally refer to any medium ormedia used to provide instructions to the processor 2010. Such machineor computer readable media associated with the module 2050 may comprisea computer software product. It should be appreciated that a computersoftware product comprising the module 2050 may also be associated withone or more processes or methods for delivering the module 2050 to thecomputing machine 2000 via the network 2080, any signal-bearing medium,or any other communication or delivery technology. The module 2050 mayalso comprise hardware circuits or information for configuring hardwarecircuits such as microcode or configuration information for an FPGA orother PLD.

The input/output (“I/O”) interface 2060 may be configured to couple toone or more external devices, to receive data from the one or moreexternal devices, and to send data to the one or more external devices.Such external devices along with the various internal devices may alsobe known as peripheral devices. The I/O interface 2060 may include bothelectrical and physical connections for operably coupling the variousperipheral devices to the computing machine 2000 or the processor 2010.The I/O interface 2060 may be configured to communicate data, addresses,and control signals between the peripheral devices, the computingmachine 2000, or the processor 2010. The I/O interface 2060 may beconfigured to implement any standard interface, such as small computersystem interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel,peripheral component interconnect (“PCI”), PCI express (PCIe), serialbus, parallel bus, advanced technology attached (“ATA”), serial ATA(“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, variousvideo buses, and the like. The I/O interface 2060 may be configured toimplement only one interface or bus technology. Alternatively, the I/Ointerface 2060 may be configured to implement multiple interfaces or bustechnologies. The I/O interface 2060 may be configured as part of, allof, or to operate in conjunction with, the system bus 2020. The I/Ointerface 2060 may include one or more buffers for bufferingtransmissions between one or more external devices, internal devices,the computing machine 2000, or the processor 2010.

The I/O interface 2060 may couple the computing machine 2000 to variousinput devices including mice, touch-screens, scanners, electronicdigitizers, sensors, receivers, touchpads, trackballs, cameras,microphones, keyboards, any other pointing devices, or any combinationsthereof. The I/O interface 2060 may couple the computing machine 2000 tovarious output devices including video displays, speakers, printers,projectors, tactile feedback devices, automation control, roboticcomponents, actuators, motors, fans, solenoids, valves, pumps,transmitters, signal emitters, lights, and so forth.

The computing machine 2000 may operate in a networked environment usinglogical connections through the network interface 2070 to one or moreother systems or computing machines across the network 2080. The network2080 may include wide area networks (WAN), local area networks (LAN),intranets, the Internet, wireless access networks, wired networks,mobile networks, telephone networks, optical networks, or combinationsthereof. The network 2080 may be packet switched, circuit switched, ofany topology, and may use any communication protocol. Communicationlinks within the network 2080 may involve various digital or an analogcommunication media such as fiber optic cables, free-space optics,waveguides, electrical conductors, wireless links, antennas,radio-frequency communications, and so forth.

The processor 2010 may be connected to the other elements of thecomputing machine 2000 or the various peripherals discussed hereinthrough the system bus 2020. It should be appreciated that the systembus 2020 may be within the processor 2010, outside the processor 2010,or both. According to some embodiments, any of the processor 2010, theother elements of the computing machine 2000, or the various peripheralsdiscussed herein may be integrated into a single device such as a systemon chip (“SOC”), system on package (“SOP”), or ASIC device.

In situations in which the systems discussed here collect personalinformation about users, or may make use of personal information, theusers may be provided with an opportunity or option to control whetherprograms or features collect user information (e.g., information about auser's social network, social actions or activities, profession, auser's preferences, or a user's current location), or to control whetherand/or how to receive content from the content server that may be morerelevant to the user. In addition, certain data may be treated in one ormore ways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over how information is collected about the userand used by a content server.

Embodiments may comprise a computer program that embodies the functionsdescribed and illustrated herein, wherein the computer program isimplemented in a computer system that comprises instructions stored in amachine-readable medium and a processor that executes the instructions.However, it should be apparent that there could be many different waysof implementing embodiments in computer programming, and the embodimentsshould not be construed as limited to any one set of computer programinstructions. Further, a skilled programmer would be able to write sucha computer program to implement an embodiment of the disclosedembodiments based on the appended flow charts and associated descriptionin the application text. Therefore, disclosure of a particular set ofprogram code instructions is not considered necessary for an adequateunderstanding of how to make and use embodiments. Further, those skilledin the art will appreciate that one or more aspects of embodimentsdescribed herein may be performed by hardware, software, or acombination thereof, as may be embodied in one or more computingsystems. Moreover, any reference to an act being performed by a computershould not be construed as being performed by a single computer as morethan one computer may perform the act.

The example embodiments described herein can be used with computerhardware and software that perform the methods and processing functionsdescribed herein. The systems, methods, and procedures described hereincan be embodied in a programmable computer, computer-executablesoftware, or digital circuitry. The software can be stored oncomputer-readable media. For example, computer-readable media caninclude a floppy disk, RAM, ROM, hard disk, removable media, flashmemory, memory stick, optical media, magneto-optical media, CD-ROM, etc.Digital circuitry can include integrated circuits, gate arrays, buildingblock logic, field programmable gate arrays (FPGA), etc.

The example systems, methods, and acts described in the embodimentspresented previously are illustrative, and, in alternative embodiments,certain acts can be performed in a different order, in parallel with oneanother, omitted entirely, and/or combined between different exampleembodiments, and/or certain additional acts can be performed, withoutdeparting from the scope and spirit of various embodiments. Accordingly,such alternative embodiments are included in the invention claimedherein.

Although specific embodiments have been described above in detail, thedescription is merely for purposes of illustration. It should beappreciated, therefore, that many aspects described above are notintended as required or essential elements unless explicitly statedotherwise. Modifications of, and equivalent components or actscorresponding to, the disclosed aspects of the example embodiments, inaddition to those described above, can be made by a person of ordinaryskill in the art, having the benefit of the present disclosure, withoutdeparting from the spirit and scope of embodiments defined in thefollowing claims, the scope of which is to be accorded the broadestinterpretation so as to encompass such modifications and equivalentstructures.

What is claimed is:
 1. A computer-implemented method for extractingfinancial card information, comprising: receiving, by one or morecomputing devices, a digital image of a financial card; applying, by theone or more computing devices, an optical character recognitionalgorithm to the digital image of the financial card to obtain a result;identifying, by the one or more computing devices, a name associatedwith the card based on information obtained via application of theoptical character recognition algorithm to the digital image of thefinancial card; determining, the one or more computing devices, a set ofuser data that indicates the identity of a user; comparing, by the oneor more computing devices, the identified name to the set of user datafor the user to determine that the name correlates to the identity ofthe user in data from the set of user data; and determining, by the oneor more computing devices, a confidence level of the result of theoptical character recognition algorithm based at least in part on thedetermination that the name correlates to the identity of the user inthe data from the set of user data.
 2. The method of claim 1, whereinthe set of user data comprises one or more of a contact list of theuser, social network data of the user, or email application data of theuser.
 3. The method of claim 1, further comprising reapplying, by theone or more computing devices, the optical character recognitionalgorithm to the digital image of the financial card upon adetermination that the confidence level is below a preconfiguredthreshold.
 4. The method of claim 1, further comprising: requesting, bythe one or more computing devices, an input of a revision of theidentified name upon a determination that the confidence level is belowa threshold validation; and receiving, by the one or more computingdevices, the input of the revision of the identified name.
 5. The methodof claim 1, wherein the card comprises a credit card, a debit card, anidentification card, a loyalty card, an access card, or a stored valuecard.
 6. A computer program product, comprising: a non-transitorycomputer-readable storage device having computer-executable programinstructions embodied thereon that when executed by a computer cause thecomputer to extract financial card information, comprising:computer-readable program instructions to receive a digital image of afinancial card; computer-readable program instructions to apply anoptical character recognition algorithm to the digital image of thefinancial card to obtain a result; computer-readable programinstructions to identify a name associated with the card based oninformation obtained via application of the optical characterrecognition algorithm to the digital image of the financial card;computer-readable program instructions to determine a set of user datathat indicates the identity of the user; computer-readable programinstructions to compare the identified name to the set of user data forthe user to determine that the name correlates to the identity of theuser in data from the set of user data; and computer-readable programinstructions to determine a confidence level of the result of theoptical character recognition algorithm based at least in part on thedetermination that the name correlates to the identity of the user inthe data from the set of user data.
 7. The computer program product ofclaim 6, wherein the set of user data comprises one or more of a contactlist of the user, social network data of the user, or data from otherfinancial accounts of the user.
 8. The computer program product of claim6, further comprising computer-executable program instructions toreapply the optical character recognition algorithm to the digital imageof the financial card upon a determination that the confidence level isbelow a preconfigured threshold.
 9. The computer program product ofclaim 6, further comprising: computer-readable program instructions torequest an input of a revision of the identified name upon adetermination that the confidence level is below a threshold validation;and computer-readable program instructions to receive the input of therevision of the identified name.
 10. The computer program product ofclaim 6, wherein the card comprises a credit card, a debit card, anidentification card, a loyalty card, an access card, or a stored valuecard.
 11. A system to extract financial card information, the systemcomprising: a storage resource; a processor communicatively coupled tothe storage resource, wherein the processor is configured to executecomputer-readable instructions that are stored in the storage resourceand that cause the system to: receive a digital image of a financialcard; apply an optical character recognition algorithm to the digitalimage of the financial card to obtain a result; identify a nameassociated with the card based on information obtained via applicationof the optical character recognition algorithm to the digital image ofthe financial card; determine a set of user data that indicates theidentity of the user; compare the identified name to the set of userdata for the user to determine that the user name correlates to theidentity of the user in data from the set of user data; and determine aconfidence level of the result of the optical character recognitionalgorithm based at least in part on the determination that the namecorrelates to the identity of the user in the data from the set of userdata.
 12. The system of claim 11, wherein the set of user data comprisesone or more of a contact list of the user, social network data of theuser, or email application data of the user.
 13. The system of claim 11,further comprising computer-executable program instructions that causethe system to reapply the optical character recognition algorithm to thedigital image of the financial card upon a determination that theconfidence level is below a preconfigured threshold.
 14. The system ofclaim 11, wherein the card comprises a credit card, a debit card, anidentification card, a loyalty card, an access card, or a stored valuecard.
 15. The system of claim 11, further comprising computer-executableprogram instructions that cause the system to: request an input of arevision of the identified user name upon a determination that theconfidence level is below a threshold validation; and receive the inputof the revision of the identified name.